DOC-4985 added section about restricting privileges #1290
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Contributor
Contributor
Author
|
Thanks @dwdougherty ! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
DOC-4985
The info in the new "Limiting privileges" and "Revoking existing privileges" sections mainly comes from George's technical note, but I've also attempted to tie the new content in with the existing example.
Hopefully this works OK, but let me know if are any errors or possible improvements. In particular, Yaron's comments on the technical note mention privileges for the
signalstable and theV_$XXXtables. Maybe in the main example, we should set privileges onsignalsexplicitly, like we do with theV_$XXXtables?